@musitdev

Because we are trying to make this programmable via the Config (MovementConfig) directly, it is written to the expected location before the application composition starts. Currently, whatever we are doing seems to cause no genesis:

"chain_id":27,"epoch":"0","ledger_version":"0","oldest_ledger_version":"0","ledger_timestamp":"0","node_role":"validator","oldest_block_height":"0","block_height":"0","git_hash":"1d1cdbbd7fabb80dcb95ba5e23213faa072fab67"}

This causes the faucet to fail, of course.

Could you compare and suggest what might be wrong that is not satisfying something that would usually occur during the setup:

• movement-migration/util/movement/core/src/movement.rs

  Line 333 in 336e52e

  pub fn container_movement_config(&self) -> Result<MovementConfig, MovementError> {

• https://github.com/movementlabsxyz/movement/blob/44c04440c01879ff4614360d471abae3eeaa11af/networks/movement/movement-full-node/src/setup/all/mod.rs#L10

What is the command you use to see this behaviour?

What is the command you use to see this behaviour?

@musitdev

You can use:

cargo test -p movement-core

This pretty much shows up anywhere you use the movement-core lib though.

@musitdev still need your ideas here.